AI Prompt Library

Consulting Proposal Template
1  Start a chat in ChatGPT, Claude, or Gemini and attach two files from your kit folder: Consulting Proposal Template 16x9.pptx and Consulting Proposal Template Map.txt 2  Copy any prompt below, paste it into the chat, and answer its questions
Built for the SlideStart Consulting Proposal Template · 16:9 build, 306 slides (June 2026) · 305 slides mapped with measured word limits · in tools that can run code, deck prompts return the assembled .pptx
Send feedbackopens your mail app — or email team@slidestart.com
Slide 1 of the Consulting Proposal Template

One prompt runs the entire build: it interviews you, reads anything you attach, plans the deck from this template's layouts, then writes every slide — and in ChatGPT or Claude, hands back the assembled .pptx.

Client proposal
The full consulting proposal: situation, approach, team, investment, the ask.
15–20 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a client proposal using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Who is the client, what do they do, and what's happening in their business right now?
2. What are you proposing to do for them, and why now?
3. Who decides, and what does each decision-maker care about?
4. What's your approach — phases or workstreams, with the names you want to use?
5. Timeline and team?
6. Fees or investment, if you want that slide drafted?
7. Why you — differentiators and proof points (past results, similar clients)?
8. What key numbers do you have (their baseline, the value at stake)? Paste or attach anything useful.
Finish with three build questions: how many slides (suggest 15–20); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: their situation -> why act now (price the status quo) -> your approach -> plan and timeline -> team and proof -> investment -> the ask. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a client proposal using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Who is the client, what do they do, and what's happening in their business right now?
2. What are you proposing to do for them, and why now?
3. Who decides, and what does each decision-maker care about?
4. What's your approach — phases or workstreams, with the names you want to use?
5. Timeline and team?
6. Fees or investment, if you want that slide drafted?
7. Why you — differentiators and proof points (past results, similar clients)?
8. What key numbers do you have (their baseline, the value at stake)? Paste or attach anything useful.
Finish with three build questions: how many slides (suggest 15–20); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: their situation -> why act now (price the status quo) -> your approach -> plan and timeline -> team and proof -> investment -> the ask. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Investment recommendation
An IC memo or investment case: thesis, market, plan, projections, risks, recommendation.
12–18 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a investment recommendation using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What is the investment or deal, in one sentence?
2. The headline numbers: size, expected returns, multiple, hold period?
3. The thesis: why does this win?
4. Key facts on the asset or opportunity, and the market around it?
5. The business plan after the investment?
6. The main risks, honestly?
7. What approval or decision do you need, from whom?
8. Attach or paste any model outputs, comps, or data — I'll map them to chart slides.
Finish with three build questions: how many slides (suggest 12–18); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: executive summary and thesis -> the opportunity -> market evidence -> the plan -> financial projections (this deck should be chart-heavy: prefer 201, 205, 207, 236) -> risks (169) -> recommendation and ask. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a investment recommendation using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What is the investment or deal, in one sentence?
2. The headline numbers: size, expected returns, multiple, hold period?
3. The thesis: why does this win?
4. Key facts on the asset or opportunity, and the market around it?
5. The business plan after the investment?
6. The main risks, honestly?
7. What approval or decision do you need, from whom?
8. Attach or paste any model outputs, comps, or data — I'll map them to chart slides.
Finish with three build questions: how many slides (suggest 12–18); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: executive summary and thesis -> the opportunity -> market evidence -> the plan -> financial projections (this deck should be chart-heavy: prefer 201, 205, 207, 236) -> risks (169) -> recommendation and ask. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Strategy presentation
Where we are, why change, the strategy, the roadmap, the ask.
15–20 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a strategy presentation using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Whose strategy is this, and who's the audience?
2. Where are you today — the honest numbers?
3. What's forcing the change, and what does standing still cost?
4. The vision or targets?
5. The strategy's pillars or big moves, with your names for them?
6. The roadmap — waves or phases?
7. Investment required and expected returns?
8. Key risks, and any data you can attach?
Finish with three build questions: how many slides (suggest 15–20); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: where we are -> why change -> vision and targets -> the pillars -> roadmap -> financials -> risks -> the ask. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a strategy presentation using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Whose strategy is this, and who's the audience?
2. Where are you today — the honest numbers?
3. What's forcing the change, and what does standing still cost?
4. The vision or targets?
5. The strategy's pillars or big moves, with your names for them?
6. The roadmap — waves or phases?
7. Investment required and expected returns?
8. Key risks, and any data you can attach?
Finish with three build questions: how many slides (suggest 15–20); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: where we are -> why change -> vision and targets -> the pillars -> roadmap -> financials -> risks -> the ask. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Board or steering update
Progress vs. plan, KPIs, issues, and the decisions you need.
8–12 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a board or steering update using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What program or period is this update covering, and for which audience?
2. Plan vs. actual — the numbers?
3. What went well that deserves a slide?
4. What's off track, and why — the honest version?
5. What decisions do you need from this group today?
6. Which KPIs does this group track? Paste or attach the latest values.
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: headline (one statement slide) -> KPIs at a glance (27/28 or charts) -> progress vs. plan -> what's off track and the fix -> risks -> decisions needed today. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a board or steering update using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What program or period is this update covering, and for which audience?
2. Plan vs. actual — the numbers?
3. What went well that deserves a slide?
4. What's off track, and why — the honest version?
5. What decisions do you need from this group today?
6. Which KPIs does this group track? Paste or attach the latest values.
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: headline (one statement slide) -> KPIs at a glance (27/28 or charts) -> progress vs. plan -> what's off track and the fix -> risks -> decisions needed today. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Pitch deck
Problem, solution, traction, market, model, team, ask.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a pitch deck using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. The company in one sentence?
2. The problem, and who feels it most?
3. Your product or solution, and what makes it hard to copy?
4. Traction — the numbers so far?
5. Market size and how you get to it?
6. Business model and unit economics?
7. The team?
8. The ask — how much, for what milestones?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the problem -> the solution -> traction (stats and charts) -> market -> model -> team -> the ask. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a pitch deck using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. The company in one sentence?
2. The problem, and who feels it most?
3. Your product or solution, and what makes it hard to copy?
4. Traction — the numbers so far?
5. Market size and how you get to it?
6. Business model and unit economics?
7. The team?
8. The ask — how much, for what milestones?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the problem -> the solution -> traction (stats and charts) -> market -> model -> team -> the ask. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Turn my data or document into a deck
Attach a spreadsheet, report, or notes — get a deck built around them.
10–16 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a turn my data or document into a deck using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Attach or paste your material first (spreadsheet, report, notes — anything).
2. What is this deck's job, and who is the audience?
3. What's the single takeaway someone should leave with?
4. Anything the material doesn't say that you know matters?
Finish with three build questions: how many slides (suggest 10–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: let the material drive. Lead each section with the chart, stat, or table layout that fits the data's actual shape, and use narrative layouts (Text + insight group) to frame what each number means. State the takeaway on slide one. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a turn my data or document into a deck using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Attach or paste your material first (spreadsheet, report, notes — anything).
2. What is this deck's job, and who is the audience?
3. What's the single takeaway someone should leave with?
4. Anything the material doesn't say that you know matters?
Finish with three build questions: how many slides (suggest 10–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: let the material drive. Lead each section with the chart, stat, or table layout that fits the data's actual shape, and use narrative layouts (Text + insight group) to frame what each number means. State the takeaway on slide one. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
RFP response
A structured response deck that mirrors the RFP's own requirements.
15–25 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a rfp response using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Attach or paste the RFP (or its requirements list) first.
2. Who's evaluating, and what do you know about their scoring?
3. Your approach, with the names you'll use?
4. Your differentiators and proof for THIS scope?
5. Team, timeline, and commercial structure?
6. Any compliance or format requirements the response must follow?
Finish with three build questions: how many slides (suggest 15–25); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: mirror the RFP's requested structure where it dictates one; otherwise understanding of need -> approach mapped to their requirements -> team -> proof -> commercials -> compliance summary. Every requirement in the RFP gets a visible home. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a rfp response using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Attach or paste the RFP (or its requirements list) first.
2. Who's evaluating, and what do you know about their scoring?
3. Your approach, with the names you'll use?
4. Your differentiators and proof for THIS scope?
5. Team, timeline, and commercial structure?
6. Any compliance or format requirements the response must follow?
Finish with three build questions: how many slides (suggest 15–25); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: mirror the RFP's requested structure where it dictates one; otherwise understanding of need -> approach mapped to their requirements -> team -> proof -> commercials -> compliance summary. Every requirement in the RFP gets a visible home. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Project kickoff
Align the team and client on scope, plan, roles, and ways of working.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a project kickoff using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's the project and who's in the room for kickoff?
2. Scope — and just as important, what's out of scope?
3. The plan: phases, milestones, key dates?
4. Who does what — both sides? Named owners?
5. Ways of working: meetings, tools, decision rights, escalation?
6. The risks you already see?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: why we're here (the goal in the client's numbers) -> scope in/out -> the plan (timeline or Gantt) -> roles on both sides -> ways of working -> risks -> first two weeks. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a project kickoff using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's the project and who's in the room for kickoff?
2. Scope — and just as important, what's out of scope?
3. The plan: phases, milestones, key dates?
4. Who does what — both sides? Named owners?
5. Ways of working: meetings, tools, decision rights, escalation?
6. The risks you already see?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: why we're here (the goal in the client's numbers) -> scope in/out -> the plan (timeline or Gantt) -> roles on both sides -> ways of working -> risks -> first two weeks. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Business review (QBR)
Results vs. plan for the period, lessons, and next period's priorities.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a business review (qbr) using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What period, what account or program, and who attends?
2. The numbers: plan vs. actual? Attach or paste them.
3. Wins worth a slide, and what drove them?
4. Misses, honestly, and the causes?
5. What changes next period?
6. Any decisions or renewals in play?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: headline of the period -> scorecard (stat grid or charts) -> wins and drivers -> misses and fixes -> next period's plan -> decisions needed. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a business review (qbr) using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What period, what account or program, and who attends?
2. The numbers: plan vs. actual? Attach or paste them.
3. Wins worth a slide, and what drove them?
4. Misses, honestly, and the causes?
5. What changes next period?
6. Any decisions or renewals in play?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: headline of the period -> scorecard (stat grid or charts) -> wins and drivers -> misses and fixes -> next period's plan -> decisions needed. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Findings readout
Mid-engagement: what the diagnostic found and what it means.
12–16 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a findings readout using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What was the diagnostic and what did it cover?
2. The findings — paste or attach the analysis?
3. Which findings surprised the client (or will)?
4. What do the findings imply we do next?
5. Any sacred cows the findings touch? How direct can I be?
Finish with three build questions: how many slides (suggest 12–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: what we examined and how (method credibility) -> findings ordered by importance, each with its evidence exhibit -> what the findings mean together -> implications and options -> recommended next phase. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a findings readout using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What was the diagnostic and what did it cover?
2. The findings — paste or attach the analysis?
3. Which findings surprised the client (or will)?
4. What do the findings imply we do next?
5. Any sacred cows the findings touch? How direct can I be?
Finish with three build questions: how many slides (suggest 12–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: what we examined and how (method credibility) -> findings ordered by importance, each with its evidence exhibit -> what the findings mean together -> implications and options -> recommended next phase. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Final recommendations
End of engagement: the answer, the evidence, and the handoff.
14–18 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a final recommendations using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What was the engagement and its original question?
2. The recommendation, in one sentence?
3. The evidence trail — attach the analysis?
4. The implementation path and who owns it after we leave?
5. Expected value and the tracking mechanism?
6. Where might this stall after handoff?
Finish with three build questions: how many slides (suggest 14–18); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the question we were asked -> the answer up front -> the evidence (chart-heavy) -> the implementation roadmap -> value and how it's tracked -> handoff owners -> risks after we leave. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a final recommendations using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What was the engagement and its original question?
2. The recommendation, in one sentence?
3. The evidence trail — attach the analysis?
4. The implementation path and who owns it after we leave?
5. Expected value and the tracking mechanism?
6. Where might this stall after handoff?
Finish with three build questions: how many slides (suggest 14–18); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the question we were asked -> the answer up front -> the evidence (chart-heavy) -> the implementation roadmap -> value and how it's tracked -> handoff owners -> risks after we leave. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Workshop or working session
A deck that runs a session: frames, exercises, and captures decisions.
10–16 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a workshop or working session using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's the session for, how long, and who's in the room?
2. What must be DECIDED or PRODUCED by the end?
3. What pre-work or inputs exist? Attach anything useful.
4. The exercises or discussion blocks you have in mind — or should I propose them?
5. Who facilitates, and how interactive can this get?
Finish with three build questions: how many slides (suggest 10–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the goal on slide one -> framing content (short) -> exercise/discussion slides with clear instructions and timeboxes -> a capture slide per decision -> commitments and owners at the end. Working slides stay sparse; this deck supports conversation, it doesn't give a speech. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a workshop or working session using my SlideStart Consulting Proposal Template.

I've attached "Consulting Proposal Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's the session for, how long, and who's in the room?
2. What must be DECIDED or PRODUCED by the end?
3. What pre-work or inputs exist? Attach anything useful.
4. The exercises or discussion blocks you have in mind — or should I propose them?
5. Who facilitates, and how interactive can this get?
Finish with three build questions: how many slides (suggest 10–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the goal on slide one -> framing content (short) -> exercise/discussion slides with clear instructions and timeboxes -> a capture slide per decision -> commitments and owners at the end. Working slides stay sparse; this deck supports conversation, it doesn't give a speech. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.

AI Prompt Library · 16:9 build, 306 slides (June 2026) · Works with ChatGPT, Claude, and Gemini.  ·  Send feedback (team@slidestart.com)